1. Scope

The scope of this document is the state-less protocol between a CalDAV client and server. We will address boundary protocol exchanges, where appropriate for clarity. CalDAV server to server protocol is out of scope.

This document assumes the following:

• That all client to server protocol users are within a single authentication domain, either on a single server, or part of a calendar domain, well known and/or under local control. i.e.: user and server “lookups” are configured correctly and will resolve, in all cases, and that resolution to a principal identifier, as used by the CalDAV protocol is also correctly configured and working. By “remote” user or server, we mean not the one that your client is connected to, but still within the authentication domain and/or accessible by a known URI, using the same principal identifier. Scheduling with external users and servers, i.e.: ones outside of your authentication domain and control, is not covered in this document. This will be addressed by separate requirements defined by the Realtime Technical Committee.